Before understanding what is risk based testing you should know what a risk is. A risk is something that has not happened yet and it may never happen in future as well, however, it is the potential problem.
We need to handle risk because if it happens then it may cause very negative impact.
In risk based testing we organize our testing efforts in such fashion that it reduces the level of product risk at the time of shipment.
Risk based testing uses risk to prioritize the appropriate test cases during the project. It starts early in the project cycle. The risks to system quality are identified and that knowledge is used in the test planning, preparation and execution.
Risk based testing involves both mitigation and contingency.
Mitigation: Mitigation is done to reduce the likelihood of defects.
Contingency: In case if the risk becomes an outcome there should be a plan to reduce the risk impact.
Risk based testing also involves risk analysis to remove or prevent defects by non-testing activities and to select the testing activities to be performed.
For risk based testing you should start with product risk analysis. Various techniques used for this are:
- Thoroughly reading the software requirements specification, design documents and other documents.
- Brainstorming with the project stakeholders.
